Holger Levsen: RC bug a week - week 3
Last week I was in Extreamdura, Spain, polishing fai for Lenny. So I only fixed one RC bug (494243), which was affecting Lenny the day mrvn pointed me to it, but wasnt anymore when I uploaded it yesterday. The reason is simple: quite some removals of buggy packages have taken place, yay! (And gerris was one of them...)
Speaking of which, the bug count has been gone quite dramatically. According to the simple graph we are down to 310 (last week 383, the week before 428), according to this turmzimmer view we are now down to 266 (last week 339), but I have found yet a better one, according to which we are at 144 RC bugs affecting Lenny!
144 bugs ain't many for a thousand developers ;-))
Last week I pointed you to rc-alert, which helps finding buggy software you are using. Rhonda pointed out
Speaking of which, the bug count has been gone quite dramatically. According to the simple graph we are down to 310 (last week 383, the week before 428), according to this turmzimmer view we are now down to 266 (last week 339), but I have found yet a better one, according to which we are at 144 RC bugs affecting Lenny!
144 bugs ain't many for a thousand developers ;-))
Last week I pointed you to rc-alert, which helps finding buggy software you are using. Rhonda pointed out
rc-alert -d TU -o andto me, which will show RC bugs (of packages installed on your system) which are open in unstable _and_ testing. This only works in testing/lenny or with devscripts from backports.org. It won't show you which have been removed from testing though ;-) Read the rc-alert manpage for other interesting queries to hunt bugs!